Item management apparatus, item management method, and storage medium

ABSTRACT

An item management apparatus comprises an interface configured to obtain a first identifier of a first wireless device that is carried by a user and a second identifier of a second wireless device that is correlated with an item and carries out an alarm notice in response to a drive signal; a first receiver configured to receive a first signal from the first wireless device; a second receiver configured to receive a second signal from the second wireless device; and a processor configured to correlate the first identifier with the second identifier and to cause the memory to store the correlated first identifier and second identifier, if the first signal is received by the first receiver from the first wireless device corresponding to the first identifier obtained via the interface, and the second signal is received by the second receiver from the second wireless device corresponding to the second identifier obtained via the interface.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of application Ser. No. 15/017,872filed Feb. 8, 2016, the entire contents of which are incorporated hereinby reference.

This application is based upon and claims the benefit of priority fromJapanese Patent Application No. 2015-023539, filed Feb. 9, 2015, theentire contents of which are incorporated herein by reference.

FIELD

Embodiments described herein relate generally to an article managementsystem, an article management apparatus for managing an article such asa baggage deposited by a user and an article management method formanaging an article.

BACKGROUND

In an article checkroom at which baggage is kept as an article, forexample, a person in charge looks for the baggage deposited by a userafter the user who has deposited the baggage comes to the window. Thus,it takes time to hand over the baggage to the user and it is expected tobe improved.

To avoid the foregoing problem, it is conceivable to develop a system inwhich a wireless device is used to shorten the time required for thedelivery of baggage. However, even if this system is constructed, thetime for the delivery of baggage cannot be shortened in a case in whichthe wireless device malfunctions.

DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram illustrating whole structure of a baggagemanagement system;

FIG. 2 is a schematic diagram illustrating a conversion table;

FIG. 3 is a schematic diagram illustrating an ID buffer and a workingmemory;

FIG. 4 is a schematic diagram illustrating an association file;

FIG. 5 is a schematic diagram illustrating a tracking file;

FIG. 6 is a flowchart illustrating procedures of a confirmation job;

FIG. 7 is a flowchart illustrating procedures of a deposit job;

FIG. 8 is a flowchart illustrating procedures of a deposit registrationprocessing and a deposit cancellation processing;

FIG. 9 is a flowchart illustrating procedures of a tracking processing;

FIG. 10 is a flowchart illustrating procedures of a tracking processing;

FIG. 11 is a flowchart illustrating procedures of a notification job;

FIG. 12 is a schematic diagram exemplifying an ID confirmation screen;

FIG. 13 is a schematic diagram exemplifying an ID confirmation screen;

FIG. 14 is a schematic diagram exemplifying a notification screen; and

FIG. 15 is a flowchart illustrating the main operations carried out inthe deposit job according to a second embodiment.

DETAILED DESCRIPTION

In accordance with an embodiment, an article management system comprisesa transmitter for sending an electric wave, a receiver for receiving theelectric wave sent from the transmitter, an alarm for carrying out anotification operation in response to the input of a drive signal and anarticle management apparatus including an association module configuredto associate the transmitter with the alarm which corresponds to anarticle to be handed over to a user who has the transmitter on conditionthat the electric wave sent from the transmitter is being received bythe receiver, and a determination-output module configured to determinewhether or not a relative distance between the transmitter and thereceiver becomes shorter than a specific distance on condition that theelectric wave sent from the transmitter is being received by thereceiver and to output the drive signal to the alarm which is associatedwith the transmitter if the relative distance is shorter than thespecific distance.

An embodiment of an article management system in which a wireless deviceis used to shorten the delivery time of an article to achieve the highefficiency of jobs is described below with reference to the accompanyingdrawings. According to the embodiment, the article management systemconstructed at an article checkroom where a user such as a travelertemporarily deposits his or her article such as a baggage (suitcase) isexemplified.

First Embodiment

FIG. 1 is a schematic diagram illustrating whole structure of an articlemanagement system 100. The article management system 100 comprises aplurality of transmitters 110, a plurality of alarms 120 and a baggagearticle management apparatus 130 serving as an article managementapparatus.

The transmitter 110 periodically or continuously sends beacon signalswith, for example, a wireless PAN (Personal Area Network) represented byBluetooth (Registered Trademark) or ZigBee (Registered Trademark) or awireless LAN (Local Area Network). A fixed or unique ID (hereinafterreferred to as a transmitter ID) for the transmitter 110 is contained inthe beacon signal. The transmitter 110 is a kind of wireless devices forachieving a high efficiency of jobs.

The plurality of transmitters 110 are prepared at the window of anarticle checkroom and are handed over to users who respectively depositbaggage in the article checkroom. The user carries the transmitter 110while the baggage of the user is deposited in the article checkroom andreturns the transmitter 110 in exchange for the deposited baggage to getback the deposited baggage. The transmitter 110 to which a barcode 111indicating the transmitter ID thereof is attached is used.

The alarm 120 carries out a notification operation when receiving adrive signal containing a fixed or unique ID (hereinafter referred to asan alarm ID) for the alarm 120. The drive signal is sent from thebaggage management apparatus 130. The notification operation includes alight emission operation by a light source and a sounding operation by asound source. The notification operation may be carried out in such amanner that the light emission operation is firstly executed for aspecific time prior to the sounding operation, or in such a manner thatthe sounding operation is firstly executed for a specific time prior tothe light emission operation. The notification operation is stopped by,for example, turning off a manual switch. The stopped notificationoperation is not executed again unless a reset operation is executed.

The alarm 120 periodically or continuously sends beacon signals with,for example, a wireless PAN represented by Bluetooth or ZigBee or awireless LAN. The fixed or unique ID of the alarm 120 is contained inthe beacon signal. The alarm 120 is one kind of wireless devices forachieving the high efficiency of jobs.

The plurality of alarms 120 are prepared at the window of the articlecheckroom and attached to baggage deposited from the users. If a userwants to deposit more than two items of baggage, the plurality ofbaggage are placed together and only one alarm 120 is attached to one ofthe baggage. The alarm 120 may be placed at the position of the baggagebut not attached to the baggage. Each alarm 120 to which a barcode 121representing the alarm ID thereof is attached is used.

The baggage management apparatus 130 comprises a CPU (Central ProcessingUnit) 131, a ROM (Read Only Memory) 132, a RAM (Random Access Memory)133, a clock section 134, an auxiliary storage device 135, an inputdevice 136, a display device 137, a barcode reader 138, a first wirelessunit 139A and a second wireless unit 139B. Further, the baggagemanagement apparatus 130 connects the CPU 131 with the ROM 132, the RAM133, the clock section 134, the auxiliary storage device 135, the inputdevice 136, the display device 137, the barcode reader 138, the firstwireless unit 139A and the second wireless unit 139B via BLs (bus lines)including an address bus line and a data bus line.

The CPU 131 acts as the center part of a computer. The CPU 131 controlseach section for realizing the functions of the baggage managementapparatus 130 according to an operating system or application programs.

The ROM 132 acts as the main memory part of the computer. The ROM 132stores the foregoing operating system or application programs. The ROM132 also stores the data needed by the CPU 131 to execute variousprocessing for controlling each section in some cases.

The RAM 133 acts as the main memory part of the computer. The RAM 133stores the data needed by the CPU 131 to execute various processing.Further, the RAM 133 can also function as a working area for the CPU 131to rewrite information properly.

The clock section 134 counts the system time (date and time) of thecomputer as the current date and time.

The auxiliary storage device 135 acting as the auxiliary storage part ofthe computer is, for example, an EEPROM (Electric Erasable ProgrammableRead-Only Memory), an HDD (Hard Disk Drive) or an SSD (Solid StateDrive). The auxiliary storage unit 135 stores the data used by the CPU131 to execute various processing or the data generated by the CPU 131in various processing. The auxiliary storage device 135 also stores theforegoing application programs in some cases.

The input device 136 receives the input of an instruction by anoperator. The display device 137 displays various screens. The displaydevice 136 is, for example, a keyboard, a mouse and the like. Thedisplay device 137 may be, for example, a liquid crystal display. Theinput device 136 and the display device 137 may be integrated with theuse of a touch panel.

The barcode reader 138 optically reads the barcodes 111 and 121 whichare respectively attached to the transmitter 110 and the alarm 120.

The first wireless unit 139A is connected with an antenna ANT1 to usethe electric wave transmission area of the antenna ANT1 as a wirelesscommunication area. The wireless unit 139A receives a beacon signal sentfrom a transmitter 110 or alarm 120 existing in the wirelesscommunication area. The antenna ANT1 is mounted nearby the window of thearticle checkroom. By using the antenna ANT1 with directivity, thebaggage management apparatus 130 can widely set the wirelesscommunication area in the direction of the directivity of the antennaANT1 based on the window. By using the antenna ANT1 withnon-directivity, the baggage management apparatus 130 can set thewireless communication area concentrically from the window acting as acenter. The antenna ANT1 and the wireless unit 139A function as thereceiver for receiving the electric wave wirelessly sent from thetransmitter 110. The wireless unit 139A comprises an intensity detectioncircuit 140. The intensity detection circuit 140 detects the intensity(db) of the electric wave received by the antenna ANT1.

The second wireless unit 139B is connected with an antenna ANT2 to usethe electric wave propagation area of the antenna ANT2 as a wirelesscommunication area. The wireless unit 139B transmits a drive signal tothe alarm 120 existing in the wireless communication area. Other thanthe general antennas, for example, a leakage coaxial cable which is laidon the ceiling of a place for baggage may also be used as the antennaANT2.

The baggage management apparatus 130 with the foregoing structure may bea computer such as a personal computer or a tablet computer terminal. Ina case in which the computer of this kind is used as the baggagemanagement apparatus 130, the barcode reader 138 is connected with thebaggage management apparatus 130 via a peripheral device interface suchas a USB. Further, the computer (the baggage management apparatus 130)is placed at the window of the article checkroom.

The baggage management apparatus 130 has three job modes, i.e., aconfirmation job, a deposit job and a notification job. The baggagemanagement apparatus 130 can execute the three jobs in parallel. Thethree jobs are controlled by different application programsrespectively.

Further, at the time of carrying out each of the three jobs, the baggagemanagement apparatus 130 needs a conversion table 200 shown in FIG. 2,an ID buffer 300 and a pair of working memories WM1 and WM2 shown inFIG. 3, an association file 400 shown in FIG. 4 and a tracking file 500shown in FIG. 5.

The conversion table 200 is a data table for the conversion of theintensity (db) of the electric wave received by the antenna ANT1 from atransmitter 110 into the relative distance (m) between the transmitter110 and the antenna ANT1. For example, at the time the baggagemanagement system 100 is introduced, a relative distance (m)corresponding to the electric wave intensity (db) is experimentallyevaluated and set in the conversion table 200. The conversion table 200is stored in the ROM 132 or the auxiliary storage device 135.

The ID buffer 300 collectively stores the transmitter IDs or alarm IDsreceived by the wireless unit 139A within a specific time. The workingmemory WM1 temporarily stores the transmitter ID of a transmitter 110delivered to a user. The working memory WM2 temporarily stores the alarmID of an alarm 120 attached to the baggage deposited by a user.

The association file 400 is a data file in which a plurality of recordseach of which consists of a transmitter ID, an alarm ID and a depositdate and time as one record is stored. The association file 400 isformed in the auxiliary storage device 135 or the RAM 133.

The tracking file 500 is a data file in which a plurality of recordseach of which consists of a transmitter ID, an electric wave intensityAm (db), a distance Dn (m), a display flag F1 and a notification flag F2as one record is stored. The tracking file 500 is formed in theauxiliary storage device 135 or the RAM 133. An alarm ID associated witha transmitter ID may also be contained in the record of the trackingfile 500.

The three jobs are sequentially described below. The confirmation job isdescribed first with reference to the flowchart of FIG. 6. Theconfirmation job refers to a job of confirming the transmitter ID oralarm ID contained in a beacon signal sent from the transmitter 110 orthe alarm 120. Further, the confirmation job includes a trackingprocessing of tracking the change in the distance between the antennaANT1 and the transmitter 110 identified by the transmitter ID.

If the baggage management apparatus 130 is started, then an applicationprogram for controlling the confirmation job is started. If the programis started, then the CPU 131 starts the processing the procedures ofwhich are shown in the flowchart of FIG. 6. First, the CPU 131 waits foran interrupt signal (Act 1). For example, the interrupt signal isgenerated for every time that one minute counted by the clock section134 elapses.

If the interrupt signal is detected (Act 1: Yes), then the CPU 131starts a built-in timer (Act 2). Further, the CPU 131 clears the IDbuffer 300 (Act 3). Not limited to be carried out in the foregoingsequence (Act 2 and ACT 3), the processing in Act 3 may be carried outprior to the processing in Act 2.

The CPU 131 waits for the timeout of the timer (Act 4). Further, the CPU131 determines whether a beacon signal is received (Act 5). If a beaconsignal is received (Act 5: Yes) prior to the timeout of the timer (Act4: No), the CPU 131 detects a transmitter ID or an alarm ID from thebeacon signal (Act 6). If no transmitter ID or alarm ID is detected (Act6: No), the CPU 131 waits for the timeout of the timer (Act 4) or waitsto receive the next beacon signal (Act 5).

If a transmitter ID or alarm ID is detected (Act 6: Yes), the CPU 131determines whether or not the detected ID is a new ID which is notregistered in the ID buffer 300 (Act 7). If the ID detected is not a newID (Act 7: No), the CPU 131 waits for the timeout of the timer (Act 4)or waits to receive the next beacon signal (Act 5).

If the ID detected is a new ID (Act 7: Yes), the CPU 131 acquires theelectric wave intensity An (db) detected by the intensity detectioncircuit 140 (Act 8). The CPU 131 determines whether or not the electricwave intensity An is equal to or greater than a threshold value A0 (Act9). The threshold value A0 is the minimal value of the electric waveintensity detected when the beacon signals sent from the plurality oftransmitters 110 or alarms 120 prepared at the window of the articlecheckroom are received by the antenna ANT1. The minimal value (thresholdvalue A0) is experimentally evaluated.

If the electric wave intensity An is equal to or greater than thethreshold value A0 (Act 9: Yes), then it is presumed that thetransmitter 110 or the alarm 120 which is a source of the beacon signalis one of the plurality of transmitters 110 or alarms 120 prepared atthe window of the article checkroom. In this case, the CPU 131 storesthe ID (transmitter ID or alarm ID) detected from the beacon signal inthe ID buffer 300 (Act 10).

If the electric wave intensity An is less than the threshold value A0(Act 9: No), then it is presumed that the transmitter 110 or the alarm120 which is a source of the beacon signal is far away from the windowof the article checkroom or is one generating a weak output under afailure in operation. In this case, the CPU 131 does not carry out theprocessing in Act 10. The CPU 131 discards the ID (transmitter ID oralarm ID) detected from the beacon signal without storing the ID in theID buffer 300.

The CPU 131 determines whether or not the ID detected from the beaconsignal is a transmitter ID (Act 11). Different category flags arecontained in the transmitter ID attached to each transmitter 110 and thealarm ID attached to each alarm 120. The CPU 131 determines whether theID detected is a transmitter ID or an alarm ID by identifying thecategory flag contained in the ID detected. Further, not limited to bedetermined according to a category flag, a transmitter ID or an alarm IDmay also be identified according to the format of the ID which isdifferent between the transmitter ID and the alarm ID.

If the detected ID is not a transmitter ID but an alarm ID (Act 11: No),the CPU 131 waits for the timeout of the timer (Act 4) or waits toreceive the next beacon signal (Act 5). If the detected ID is atransmitter ID (Act 11: Yes), the CPU 131 carries out a trackingprocessing (Act 12). The tracking processing will be described in detaillater. If the tracking processing is ended, the CPU 131 waits for thetimeout of the timer (Act 4) or waits to receive the next beacon signal(Act 5).

If the timer takes timeout (Act 4: Yes), then the CPU 131 returns to theprocessing in Act 1 to wait for the next interrupt signal. Afterwards,the CPU 131 repeats the processing in Act 2-Act 12 every time theinterrupt signal is received.

Then, the deposit job is described with reference to the flowcharts inFIG. 7 and FIG. 8.

If the baggage management apparatus 130 is activated, then anapplication program for controlling the deposit job is started. If theprogram is started, then the CPU 131 starts the processing theprocedures of which are shown in the flowchart in FIG. 7. First, the CPU131 waits for a deposit declaration (Act 21). If the input device 136 isa keyboard, then the CPU 131 waits for the input of a depositdeclaration key assigned to the keyboard. If the input device 136 is amouse, the CPU 131 waits for the click on a deposit declaration icondisplayed on the display device 137.

When a user who deposits a baggage comes to the window, a person incharge at the window operates the input device 136 to input the depositdeclaration key or clicks the deposit declaration icon. If the depositdeclaration is received (Act 21: Yes), the CPU 131 clears the pair ofworking memories WM1 and WM2 (Act 22).

The CPU 131 waits for the input of barcode data (Act 23). If a barcodeis read by the barcode reader 138 (Act 23: Yes: input module), then theCPU 131 identifies whether the barcode data is a transmitter ID (Act 24)or an alarm ID (Act 25). As stated above, different category flags arecontained in the transmitter ID attached to each transmitter 110 and thealarm ID attached to each alarm 120. The CPU 131 determines whether thebarcode data is a transmitter ID or an alarm ID by identifying thecategory flag contained in the barcode data.

If the barcode data is neither a transmitter ID (Act 24: No) nor analarm ID (Act 25: No), the CPU 131 waits for the input of next barcodedata (Act 23).

If the barcode data is a transmitter ID (Act 24: Yes), the CPU 131executes a retrieval operation in the ID buffer 300 (Act 26). Further,the CPU 131 determines whether or not an ID identical to the transmitterID identified according to the barcode data is stored in the ID buffer300 (Act 27).

The person in charge at the window who makes a deposit declaration picksout a transmitter 110 to be handed over to the user in exchange for thebaggage of the user. The person in charge operates the barcode reader138 to read the barcode 111 attached to the transmitter 110. At thistime, the transmitter 110 is one of the plurality of transmitters 110prepared at the window of the article checkroom. Thus, the transmitterID of the transmitter 110 is stored in the ID buffer 300 as long as thetransmitter 110 is not one generating a weak output under the failure inoperation.

The transmitter 110 identified by the transmitter ID is a normalwireless device if an ID identical to the transmitter ID is stored inthe ID buffer 300 (Act 27: Yes). In this case, the CPU 131 stores thetransmitter ID in the working memory WM1 (Act 28.)

If the barcode data is an alarm ID (Act 25: Yes), the CPU 131 executes aretrieval operation in the ID buffer 300 (Act 29). Further, the CPU 131determines whether or not an ID identical to the alarm ID identified bythe barcode data is stored in the ID buffer 300 (Act 30).

The person in charge of the window who makes the deposit declarationtakes out an alarm 120 to be attached to the baggage deposited by theuser. Further, the person in charge operates the barcode reader 138 toread the barcode 121 attached to the alarm 120. At this time, the alarm120 is one of the plurality of alarms 120 prepared at the window of thearticle checkroom. Thus, the alarm ID of the alarm 120 is stored in theID buffer 300 as long as the alarm 120 is not one generating a weakoutput under the failure in operation.

The alarm 120 identified by the alarm ID is a normal wireless device ifan ID identical to the alarm ID is stored in the ID buffer 300 (Act 30:Yes). In this case, the CPU 131 stores the alarm ID in the workingmemory WM2 (Act 31).

The CPU 131 determines whether or not the transmitter ID is associatedwith the alarm ID (Act 32). The CPU 131 determines that the transmitterID is associated with the alarm ID if the transmitter ID and the alarmID are respectively stored in the pair of working memories WM1 and WM2.The CPU 131 determines that the transmitter ID is not associated withthe alarm ID if only one of the transmitter ID and the alarm ID isstored. The CPU 131 waits for the input of the next barcode data (Act23) if the transmitter ID is not associated with the alarm ID (Act 32:No).

If the transmitter ID is associated with the alarm ID (Act 32: Yes), theCPU 131 displays an ID confirmation screen 600 (refer to FIG. 12) on thedisplay device 137 (Act 33).

FIG. 12 exemplifies the ID confirmation screen 600. As shown in FIG. 12,a display area 601 for customer, a display area 602 for baggage, adeposit registration button 603 and a deposit cancellation button 604are included in the ID confirmation screen 600 as display components.

The CPU 131 displays the transmitter ID stored in the working memory WM1in the display area 601 for customer. Further, the CPU 131 displays thealarm ID stored in the working memory WM2 in the display area 602 forbaggage. The CPU 131 further displays a message 605 indicating that thetransmitter 110 determined by the transmitter ID and the alarm 120determined by the alarm ID are normal. Further, the deposit registrationbutton 603 and the deposit cancellation button 604 are both unavailableat a point of time. Thus, the button 603 or 604 cannot be input even ifthe person in charge at the window tries to operate the input device 136to input the button 603 or 604.

After the ID confirmation screen 600 is displayed, the CPU 131 executesa retrieval operation in the association file 400. Further, the CPU 131determines whether or not a record containing the transmitter ID storedin the working memory WM1 and the alarm ID stored in the working memoryWM2 is registered in the association file 400 (Act 35). If the record isnot registered in the association file 400 (Act 35: Yes), the CPU 131carries out a deposit registration processing (Act 36). If the record isregistered in the association file 400 (Act 35: No), the CPU 131 carriesout a deposit cancellation processing (Act 37).

The procedures of the deposit registration processing and those of thedeposit cancellation processing are shown in the flowchart of FIG. 8. Ifthe deposit registration processing is executed, the CPU 131 firstenables the function of the deposit registration button 603 on the IDconfirmation screen 600 (Act 41). Then, the CPU 131 waits for the inputof the deposit registration button 603 (Act 42).

After confirming that the transmitter 110 the barcode 111 of which isread and the alarm 120 the barcode 121 of which is read are normalaccording to the ID confirmation screen 600, the person in charge of thewindow operates the input device 136 to input the deposit registrationbutton 603.

When the deposit registration button 603 is input, the CPU 131 acquiresthe date and time data counted by the clock section 134 as the date andtime the user deposits the baggage (Act 43). Further, the CPU 131records the transmitter ID stored in the working memory WM1, the alarmID stored in the working memory WM2 and the deposit date and time dataacquired in Act 43 in the association file 400 as one record (Act 44: anassociation module). Sequentially, the CPU 131 erases the IDconfirmation screen 600 (Act 45), then the deposit registrationprocessing is ended.

On the other hand, if the deposit cancellation processing is executed,then the CPU 131 enables the function of the deposit cancellation button604 on the ID confirmation screen 600 (Act 51). Then, the CPU 131 waitsfor the input of the deposit cancellation button 604 (Act 52).

When the user who has deposited the baggage comes to receive thebaggage, the person in charge of the window reads the barcode 111 of thetransmitter 110 received from the user and the barcode of the alarm 120attached to the baggage deposited by the user with the barcode reader138. In this case also, since the transmitter 110 is located at thewindow, the transmitter ID is stored in the ID buffer 300. Similarly,since the alarm 120 is located at the window, the alarm ID is alsostored in the ID buffer 300. Thus, the ID confirmation screen 600 isdisplayed on the display device 137. Then, the person in charge of thewindow operates the input device 136 to input the deposit cancellationbutton 604.

When the deposit cancellation button 604 is input, the CPU 131 acquiresa deposit date and time from a record in the association file 400 whichcontains the transmitter ID stored in the working memory WM1 and thealarm ID stored in the working memory WM2 (Act 53). Further, the CPU 131calculates a deposit time S from the deposit date and time to thecurrent date and time counted by the clock section 134 (Act 54). Asshown in FIG. 13, the CPU 131 displays the deposit time S, together witha button ‘confirm’ 606, on the ID confirmation screen 600 (Act 55).Then, the CPU 131 waits for the input of the button ‘confirm’ 606 (Act56).

Then, after confirming the deposit time S, the person in charge of thewindow operates the input device 136 to input the button ‘confirm’ 606.When the button ‘confirm’ 606 is input (Act 56: Yes), the CPU 131deletes, from the association file 400, the record containing thetransmitter ID stored in the working memory WM1 and the alarm ID storedin the working memory WM2 (Act 57).

Further, the CPU 131 deletes, from the tracking file 500, the recordcontaining the transmitter ID stored in the working memory WM1 (Act 58).Sequentially, the CPU 131 erases the ID confirmation screen 600 (Act45). Then, the deposit cancellation processing is ended. Other thanphysically deleting the record, the record may be invalid in such amanner that a deletion flag is set on the record.

In this way, if the deposit registration processing or the depositcancellation processing is ended, then the application program forcontrolling the deposit job returns to the initial step. The CPU 131restarts the processing the procedures of which are shown in theflowchart of FIG. 7.

On the other hand, if an ID identical to the transmitter ID is not beingstored in the ID buffer 300 (Act 27: No), the transmitter 110 thebarcode 111 of which is read is determined that a beacon signal sendingfunction is out of order. Similarly, if an ID identical to the alarm IDis not stored in the ID buffer 300 (Act 30: No), the alarm 120 thebarcode 121 of which is read is also determined that a beacon signalsending function is out of order. In this case, the CPU 131 notifies theabnormality of the transmitter 110 or the alarm 120 (Act 38). Forexample, the CPU 131 displays a message indicating that the transmitter110 or the alarm 120 is out of order, together with the button ‘confirm’606, on the display device 137. The CPU 131 waits for the input of thebutton ‘confirm’ (Act 39). If the button ‘confirm’ is input through theoperation of the input device 136 (Act 39: Yes), then the CPU 131 waitsfor the input of the next barcode data (Act 23).

Then, the description of the deposit job is ended. Next, the trackingprocessing (Act 12 shown in FIG. 5) is described with reference to theflowcharts in FIG. 9 and FIG. 10.

If the tracking processing is started, the CPU 131 executes a retrievaloperation in the tracking file 500 according to the transmitter IDdetected from the beacon signal (Act 61). Further, the CPU 131determines whether or not a record containing the same transmitter ID isregistered in the tracking file 500 (Act 62). If the record is notregistered in the tracking file 500 (Act 62: No), the CPU 131 executes aretrieval operation in the association file 400 using the transmitter ID(Act 63). The CPU 131 further determines whether or not a recordcontaining the same transmitter ID is registered in the association file400 (Act 64). If a record containing the same transmitter ID is notregistered in the association file 400 (Act 64: No), the CPU 131 exitsthe tracking processing.

If a record containing the same transmitter ID is registered in theassociation file 400 (Act 64: Yes), the CPU 131 acquires a deposit dateand time data at which the baggage is deposited from the record (Act65). The CPU 131 calculates an elapsed time t between the deposit dateand time and the current date and time counted by the clock section 134(Act 66).

The CPU 131 determines whether or not the elapsed time t is longer thana determination time T (Act 67). The determination time T is a period oftime which is enough for the user who deposits the baggage to passthrough the wireless communication area of the antenna ANT1 and thus isset optionally.

If the elapsed time t is shorter than the determination time T, then thereceived transmitter ID can be considered as an ID sent from thetransmitter 110 delivered to the user who just deposits the baggage. Inthis case (Act 67: No), the CPU 131 exits the tracking processing.

If the elapsed time t is longer than the determination time T (Act 67:Yes), then the received transmitter ID can be considered as an ID sentfrom the transmitter 110 carried by the user who comes to receive thebaggage. Further, the received transmitter ID can also be considered asan ID sent from the transmitter 110 carried by the user who just entersthe wireless communication area of the antenna ANT1. In this case, theCPU 131 records a record containing the transmitter ID and the electricwave intensity An(db) in the tracking file 500 (Act 68). The CPU 131resets the display flag F1 and notification flag F2 of the record to 0(Act 69). The CPU 131 converts the electric wave intensity An (db) intothe relative distance Dn(m) between the transmitter 110 and the antennaANT1 with reference to the conversion table 200. Further, the CPU 131records the relative distance Dn(m) in the record (Act 70). Then, theCPU 131 exits the tracking processing.

If a record containing the same transmitter ID is registered in thetracking file 500 (Act 62: Yes), the CPU 131 reads the electric waveintensity Am (db) recorded in the record (Act 81), as shown in FIG. 10.Then, the CPU 131 compares the electric wave intensity Am (db) with theelectric wave intensity An (db) acquired in Act 8 (Act 82).

If the electric wave intensity An (db) is lower than the electric waveintensity Am (db), in other words, if the electric wave intensitybecomes weaker and weaker as time elapses, then it can be determinedthat the user is getting away from the window of the article checkroom.In this case (Act 82: No), the CPU 131 resets the display flag F1 of therecord to 0 (Act 83). The CPU 131 also resets the notification flag F2of the record to 0 (Act 84). Further, the CPU 131 converts the electricwave intensity An (db) to the relative distance Dn (m) between thetransmitter 110 and the antenna ANT1 with reference to the conversiontable 200. Then, the CPU 131 records the relative distance Dn (m) in therecord (Act 89). After that, the CPU 131 exits the tracking processing.

Contrarily, if the electric wave intensity An (db) is higher than theelectric wave intensity Am (db), in other words, if the electric waveintensity becomes stronger and stronger as time elapses, then it can bedetermined that the user is approaching the window of the articlecheckroom. In this case (Act 82: Yes), the CPU 131 determines whether ornot the electric wave intensity An (db) is greater than a firstthreshold value As1 (db) (Act 85). The first threshold value As1 (db)can be considered as the value of the intensity of the electric wavefrom a transmitter 110, which operates normally, positioned apart fromthe antenna ANT1 by a relative distance of, for example, 50 m.

If the electric wave intensity An (db) is lower than the first thresholdvalue As1 (db), then it can be determined that the user does not comewithin 50 m of the window. In this case (Act 85: No), the CPU 131 resetsthe display flag F1 of the record containing the received transmitter IDto 0 (Act 83). The CPU 131 also resets the notification flag F2 of therecord to 0 (Act 84). Further, the CPU 131 converts the electric waveintensity Am (db) to the relative distance Dn (m) between thetransmitter 110 and the antenna ANT1 with reference to the conversiontable 200. Then, the CPU 131 records the relative distance Dn (m) in therecord (Act 89). After that, the CPU 131 exits the tracking processing.

Contrarily, if the electric wave intensity An (db) is higher than thefirst threshold value As1 (db), then it can be determined that the usercomes within 50 m of the window. In this case (Act 85: Yes), the CPU 131sets the display flag F1 of the record containing the receivedtransmitter ID to 1 (Act 86).

Then, the CPU 131 determines whether or not the electric wave intensityAn (db) is higher than a second threshold value As2 (Act 87). The secondthreshold value As2 (db) can be considered as the value of the intensityof the electric wave received from the transmitter 110 which ispositioned apart from the antenna ANT1 by a relative distance of, forexample, 30 m.

If the electric wave intensity An (db) is lower than the secondthreshold value As2 (db), then it can be considered that the user doesnot come within 30 m of the window. In this case (Act 87: No), the CPU131 resets the notification flag F2 of the record containing thereceived transmitter ID to 0 (Act 84). Further, the CPU 131 converts theelectric wave intensity Am (db) to the relative distance Dn (m) betweenthe transmitter 110 and the antenna ANT1 with reference to theconversion table 200. Then, the CPU 131 records the relative distance Dn(m) in the record (Act 89). After that, the CPU 131 exits the trackingprocessing.

Contrarily, if the electric wave intensity An (db) is higher than thesecond threshold value As2 (db), then it can be determined that the usercomes within 30 m of the window. In this case (Act 87: Yes), the CPU 131sets the notification flag F2 of the record containing the receivedtransmitter ID to 1 (Act 88). Further, the CPU 131 converts the electricwave intensity Am (db) to the relative distance Dn (m) between thetransmitter 110 and the antenna ANT1 with reference to the conversiontable 200. Then, the CPU 131 records the relative distance Dn (m) in therecord (Act 89). After that, the CPU 131 exits the tracking processing.

Further, the first threshold value As1 and the second threshold valueAs2 can be set optionally as long as the As1 lower than the As2 is kept.

Then, the notification job is described with reference to the flowchartin FIG. 11.

An application program for controlling the notification job is startedin response to interrupt signals which are generated at a specificinterval (e.g. 1 second). If the program is started, then the CPU 131starts the processing the procedures of which are shown in the flowchartin FIG. 11. First, the CPU 131 retrieves the notification flag F2 ineach record recorded in the tracking file 500 (Act 91). Then, the CPU131 determines whether or not there is a record of which thenotification flag F2 is set to 1 (Act 92).

If there is a record of which the notification flag F2 is set to 1 (Act92: Yes), then the record is a notification target. In this case, theCPU 131 executes a retrieval operation in the association file 400according to the transmitter ID contained in the record. Then, the CPU131 detects an alarm ID associated with the transmitter ID (Act 93). TheCPU 131 sends a drive signal containing the alarm ID from the antennaANT2 via the wireless unit 139B (Act 94: a determination-output module).

Further, if there are a plurality of records of which the notificationflags are set to 1, the CPU 131 executes a retrieval operation in theassociation file 400 according to the transmitter ID contained in eachrecord to detect each alarm ID associated with the transmitter ID. TheCPU 131 respectively sends drive signals each containing a differentalarm ID from the antenna ANT2 via the wireless unit 139B in a timedivision manner.

In response to the transmission of the drive signal containing an alarmID, the alarm 120 to which the alarm ID is set carries out anotification operation with sound and light. The baggage to which thealarm 120 carrying out the notification operation is attached is onedeposited by a user who comes within 30 m of the window. In this way,the person in charge of the window or the baggage deposit place can findthe baggage deposited by the user and bring the found baggage to thewindow in advance while the user comes to the window. As a result, atime required to deliver the baggage at the window is shortened, andthus high efficiency of the jobs at the window can be achieved.

After the drive signal is sent or if there is no record of thenotification target (Act 92: No), the CPU 131 retrieves the display flagF1 in the tracking file 500 (Act 95). The CPU 131 determines whether ornot there is a record of which the display flag F1 is set to 1 (Act 96).The processing is ended if there is no record of which the display flagF1 is set to 1 (Act 96: No).

If there is a record of which the display flag F1 is set to 1 (Act 96:Yes), then the record is a display target. In this case, the CPU 131acquires a transmitter ID and a distance Dn from the record. If there isa plurality of records of which the display flags F1 are set to 1, thenthe CPU 131 acquires a transmitter ID and a distance Dn from each of therecords (Act 97). The CPU 131 displays, for example, a notificationscreen 700 the layout of which is shown in FIG. 14 on the display device137 according to the data acquired from the tracking file 500 (Act 98).

As shown in FIG. 14, transmitter IDs 701 and indicators 702 each ofwhich indicates a distance Dn (m) are displayed on the notificationscreen 700 such that the transmitter IDs 701 respectively correspond tothe indicators 702. Taking 50 m, corresponding to the first thresholdvalue As1 (db), which is a relative distance from the antenna ANT1, as areference value, the distance Dn is displayed in such a manner that theindicator 702 becomes longer as the distance Dn decreases with respectto the reference value (50 m). Thus, after confirming the notificationscreen 700, the person in charge of the window or the baggage depositplace can visually confirm the number of the users who are coming to thewindow to receive his or her baggage and the distances between the usersand the window. Thus, if there are many users who are coming to thewindow, proper measures can be taken previously. For example, morestaffs are assigned as a person in charge of the window, and thus jobsat the window can be performed more efficiently.

The layout of the notification screen 700 is not limited to that shownin FIG. 14. For example, the distance between a transmitter and theantenna ANT1 may be displayed as its actual value (digital value) butnot displayed as an indicator (analog value). Further, an alarm IDassociated with a transmitter ID other than a transmitter ID may bedisplayed.

Thus, according to the first embodiment, with the use of the transmitter110 serving as a wireless device, the period of time required to handover the baggage at the article checkroom is shortened and thus thebaggage delivery job can be performed efficiently. Further, the baggagemanagement apparatus 130 automatically checks the beacon signal sendingfunction of a transmitter 110 when the transmitter 110 is handed over toa user. Similarly, the baggage management apparatus 130 automaticallychecks the beacon signal sending function of an alarm 120 which isattached to the baggage deposited by the user. In this way, the deliveryof a transmitter 110 having a malfunction, which sends no beacon signalor a weak beacon signal, to the user is prevented, and the attachment ofan alarm 120 having the malfunction to a baggage is also prevented.Thus, a high-efficient baggage delivery job can be practicallyperformed.

Second Embodiment

Then, the second embodiment is described. The second embodiment isdifferent from the first embodiment in a part of the procedures of theconfirmation job and the deposit job.

First, the procedures of the confirmation job are described.

The confirmation job according to the second embodiment excludes theprocessing in Act 3 and Act6-Act 10 from that in the first embodiment.In FIG. 6, if an interrupt signal is detected in Act 1 (Act 1: Yes), theCPU 131 starts a built-in timer (Act 2). Then, the CPU 131 waits for thetimeout of the timer (Act 4). Further, the CPU 131 determines whether ornot a beacon signal is received (Act 5). If a beacon signal is received(Act 5: Yes) prior to the timeout of the timer (Act 4: No), the CPU 131detects a transmitter ID from the beacon signal (Act 11). If notransmitter ID is detected (Act 11: No), the CPU 131 waits for thetimeout of the timer (Act 4) or waits to receive the next beacon signal(Act 5).

If a transmitter ID is detected (Act 11: Yes), the CPU 131 carries out atracking processing (Act 12). The tracking processing is identical tothat described in the first embodiment and is therefore not describedherein repeatedly. If the tracking processing is ended, the CPU 131waits for the timeout of the timer (Act 4) or waits to receive the nextbeacon signal (Act 5).

Then, the procedures of the deposit job are described.

Procedures of the deposit job in the second embodiment are differentfrom that in the first embodiment in that the processing in Act 26 andAct 27 which are carried out after the result of the determination ofAct 24 is ‘Yes’ and the processing in Act 29 and Act 30 which arecarried out after the result of the determination of Act 25 is ‘Yes’ inthe first embodiment are replaced by the processing in Act 101-Act 107shown in FIG. 15 in the second embodiment. The CPU 131 starts thebuilt-in timer (Act 101) if it is determined in the processing in Act 24or Act 25 that the barcode data is a transmitter ID or alarm ID.Further, the CPU 131 determines whether or not a beacon signal isreceived (Act 102). If no beacon signal is received (Act 102: No), theCPU 131 determines whether or not the timer takes timeout (Act 103). Ifthe timer does not take timeout (Act 103: No), the CPU 131 returns tothe processing in Act 102 to wait for a beacon signal.

If a beacon signal is received (Act 102: Yes), the CPU 131 detects atransmitter ID or an alarm ID from the beacon signal (Act 104). If notransmitter ID or alarm ID is detected (Act 104: No), the CPU 131 waitsto receive a next beacon signal (Act 102).

If a transmitter ID or alarm ID is detected (Act 104: Yes), the CPU 131determines whether or not the detected ID is identical to thetransmitter ID or the alarm ID represented with the barcode data (Act105). If the detected ID is not identical to the transmitter ID or thealarm ID represented with the barcode data (Act 105: No), the CPU 131waits to receive a next beacon signal (Act 102).

If the detected ID is identical to the transmitter ID or the alarm IDrepresented by the barcode data (Act 105: Yes), the CPU 131 acquires theelectric wave intensity An (db) detected by the intensity detectioncircuit 140 (Act 106). The CPU 131 determines whether or not theelectric wave intensity An is greater than a threshold value A0 (Act107). The threshold value A0 is the minimal value of the electric waveintensity acquired when the beacon signals sent from the plurality oftransmitters 110 or alarms 120 prepared at the window of the articlecheckroom are received by the antenna ANT1. The minimal value (thresholdvalue A0) is experimentally evaluated.

If the electric wave intensity An is greater than the threshold value A0(Act 107: Yes), it is presumed that the source (sender) of the beaconsignal is a plurality of transmitters 110 or alarms 120 prepared at thewindow of the article checkroom. In this case, the CPU 131 stores the ID(transmitter ID or alarm ID) detected from the beacon signal in theworking memory WM1 or WM2 (Act 28 or 31). The subsequent procedures areidentical to those in the first embodiment.

On the other hand, if the timer takes timeout without receiving atransmitter ID or alarm ID coincident with that shown with the barcodedata (Act 103: Yes) or if the electric wave intensity An is equal to thethreshold value A0 (Act 107: No), the transmitter 110 or the alarm 120the barcode 121 of which is read is determined to be malfunction in abeacon signal sending function thereof. In this case, the CPU 131notifies the malfunction of the transmitter 110 or alarm 120 (Act 38).The subsequent procedures are identical to those in the firstembodiment.

The second embodiment with the foregoing structure also achieves thesame effect as achieved by the first embodiment. Further, the secondembodiment has an advantage in that the ID buffer 300 is not needed.

The present invention is not limited to the foregoing embodiments.

For example, in the foregoing embodiments, in the deposit job, thedeposit registration button 603 is enabled when a deposit registrationprocessing is executed, and the deposit cancellation button 604 isenabled when a deposit cancellation processing is executed. In thisregard, it is also applicable that the deposit registration button 603is displayed on the ID confirmation screen 600 when a depositregistration processing is executed and the deposit cancellation button604 is displayed on the ID confirmation screen 600 when a depositcancellation processing is executed. Although the deposit registrationbutton 603 and the deposit cancellation button 604 are always enabled,it may be set that an error in operation is displayed if the depositcancellation button 604 is operated in the deposit registrationprocessing or if the deposit registration button 603 is operated in thedeposit cancellation processing.

Further, in the foregoing embodiments, electric wave reception intensityis compared with a threshold value. As to this point, the electric wavereception intensity may be converted to a distance data, and thedistance data may be compared with a threshold value. Further, aconfirmation method in which whether or not the relative distancebetween the transmitter 110 and the antenna ANT1 is within a specificdistance is determined is not limited to the method which uses theelectric wave reception intensity. It is sufficient that the relativedistance between the transmitter 110 and the antenna ANT1 can beevaluated with a method.

Further, in the foregoing embodiments, a first wireless unit 139A and asecond wireless unit 139B are arranged; however, the wireless units maybe integrated. In this case, with the use of an existing communicationmethod such as Bluetooth (Registered Trademark), the communicationbetween the wireless unit and a transmitter 110 is set as unidirectionalcommunication and that between the wireless unit and the alarm 120 asbidirectional communication. Further, to guarantee a long-distancecommunication with the transmitter 110, a diversity antenna is used asthe antenna ANT1.

Further, it is exemplified in the foregoing embodiments that thereception of the deposit of an article and the delivery of the depositedarticle are executed at the same window, however, the reception of thedeposit of an article and the delivery of the deposited article are notnecessarily executed at the same window. For example, the deposit of anarticle may be received at a window located at a place A and thedeposited article is handed over to the user at a window located at aplace B different from the place A.

Further, the article management apparatus is typically delivered in astate in which a program such as an application program stored in anROM. However, the delivery of the article management apparatus is notlimited to this; a program which is delivered in other way other thanthat of the computer may be written into a writable memory device of thecomputer. The program is delivered by being recorded in a removablerecording medium or through a network communication. The recordingmedium may be in any form as long as the recording medium is capable ofstoring programs and readable to the apparatus like a CD-ROM or memorycard. Further, the functions achieved by an installed or downloadedprogram can also be achieved through the cooperation with an OS(Operating System) in an apparatus.

While certain embodiments have been described, these embodiments havebeen presented by way of example only, and are not intended to limit thescope of the invention. Indeed, the novel embodiments described hereinmay be embodied in a variety of other forms; furthermore, variousomissions, substitutions and changes in the form of the embodimentsdescribed herein may be made without departing from the spirit of theinvention. The accompanying claims and their equivalents are intended tocover such forms or modifications as would fall within the scope andspirit of the invention.

What is claimed is:
 1. An item management apparatus comprising: aninterface configured to obtain a first identifier of a first wirelessdevice that is carried by a user and a second identifier of a secondwireless device that is correlated with an item and carries out an alarmnotice in response to a drive signal; a first receiver configured toreceive a first signal from the first wireless device; a second receiverconfigured to receive a second signal from the second wireless device; amemory; and a processor configured to correlate the first identifierwith the second identifier and to cause the memory to store thecorrelated first identifier and second identifier, if the first signalis received by the first receiver from the first wireless devicecorresponding to the first identifier obtained via the interface, andthe second signal is received by the second receiver from the secondwireless device corresponding to the second identifier obtained via theinterface.
 2. The apparatus according to claim 1, wherein the firstsignal includes a third identifier of the first wireless device, thesecond signal includes a fourth identifier of the second wirelessdevice, if the first identifier of the first wireless device is obtainedvia the interface, the processor determines whether or not the firstidentifier matches a third identifier included in the first signalreceived by the first receiver, if the second identifier of the secondwireless device is obtained via the interface, the processor determineswhether or not the second identifier matches a fourth identifierincluded in the second signal received via the second receiver, and ifthe first identifier matches the third identifier and the secondidentifier matches the fourth identifier, the processor correlates thefirst identifier with the second identifier and causes the memory tostore the correlated first identifier and second identifier.
 3. Theapparatus according to claim 1, wherein if the first signal is receivedby the first receiver, the processor determines electric wave intensityof the received first signal, if the second signal is received by thesecond receiver, the processor determines electric wave intensity of thereceived second signal, and if the electric wave intensity of thereceived first signal is greater than predetermined electric waveintensity, and the electric wave intensity of the received second signalis greater than predetermined electric wave intensity, the processorcorrelates the first identifier with the second identifier and causesthe memory to store the correlated first identifier and secondidentifier.
 4. The apparatus according to claim 2, further comprising: athird receiver configured to receive the first signal from the firstwireless device; and a communication interface configured to transmitthe drive signal to cause the second wireless device to carry out analarm notice, wherein the processor determines electric wave intensityof the first wireless device based on the first signal received by thethird receiver, and if the intensity is greater than predeterminedelectric wave intensity, the processor causes the communicationinterface to transmit the drive signal.
 5. The apparatus according toclaim 2, further comprising: a buffer configured to store the thirdidentifier that is included in the first wireless device and received bythe first receiver, and the fourth identifier that is included in thesecond wireless device and received by the second receiver, wherein theprocessor determines whether the third identifier is stored in thebuffer, the third identifier matching the first identifier of the firstwireless device, the first identifier being obtained via the interface,the processor determines whether the fourth identifier is stored in thebuffer, the fourth identifier matching the second identifier of thesecond wireless device, the second identifier being obtained via theinterface, and if the third identifier that matches the first identifieris stored in the buffer and the fourth identifier that matches thesecond identifier is stored in the buffer, the processor correlates thefirst identifier with the second identifier and causes the memory tostore the correlated first identifier and second identifier.
 6. Theapparatus according to claim 2, wherein the processor activates a timerif the first identifier of the first wireless device is obtained via theinterface, and determines whether or not the first signal including thethird identifier that matches the first identifier is received by thefirst receiver until the timer takes timeout, the processor activates atimer if the second identifier of the second wireless device is obtainedvia the interface, and determines whether or not the second signalincluding the fourth identifier that matches the first identifier isreceived by the second receiver until the timer takes timeout, and ifthe first signal including the third identifier that matches the firstidentifier is received by the first receiver, and the second signalincluding the fourth identifier that matches the second identifier isreceived by the second receiver, the processor correlates the firstidentifier with the second identifier, and causes the memory to storethe correlated first identifier and second identifier.
 7. An itemmanagement method comprising: obtaining a first identifier of a firstwireless device that is carried by a user and a second identifier of asecond wireless device that carries out an alarm notice in response to adrive signal; receiving a first signal from the first wireless device;receiving a second signal from the second wireless device; and if thefirst signal is received from the first wireless device corresponding tothe obtained first identifier, and the second signal is received fromthe second wireless device corresponding to the obtained secondidentifier, correlating the first identifier with the second identifierand causing a memory to store the correlated first identifier and secondidentifier.
 8. The method according to claim 7, wherein if the firstidentifier of the first wireless device is obtained, it is determinedwhether or not the first identifier matches a third identifier of thefirst wireless device included in the received first signal, if thesecond identifier of the second wireless device is obtained, it isdetermined whether or not the second identifier matches a fourthidentifier of the second wireless device included in the received secondsignal, and if the first identifier matches the third identifier, andthe second identifier matches the fourth identifier, the firstidentifier is correlated with the second identifier and the memory iscaused to store the correlated first identifier and second identifier.9. A non-transitory storage medium having stored thereon a programreadable to a computer system, wherein the program causes the computersystem to execute a process routine of: obtaining a first identifier ofa first wireless device that is carried by a user; obtaining a secondidentifier of a second wireless device that carries out an alarm noticein response to a drive signal, the second identifier being correlatedwith an item; receiving a first signal from the first wireless device;receiving a second signal from the second wireless device; and if thefirst signal is received from the first wireless device corresponding tothe obtained first identifier, and the second signal is received fromthe second wireless device corresponding to the obtained secondidentifier, correlating the first identifier with the second identifierand causing a memory to store the correlated first identifier and secondidentifier.
 10. The non-transitory storage medium according to claim 9,wherein if the first identifier of the first wireless device isobtained, it is determined whether or not the first identifier matches athird identifier of the first wireless device included in the receivedfirst signal, if the second identifier of the second wireless device isobtained, it is determined whether or not the second identifier matchesa fourth identifier of the second wireless device included in thereceived second signal, and if the first identifier matches the thirdidentifier and the second identifier matches the fourth identifier, thefirst identifier is correlated with the second identifier and the memoryis caused to store the correlated first identifier and secondidentifier.